Default enable cluster state role mapper #114337
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
n1v0lg
added
>bug
:Security/Authentication
n1v0lg
changed the title
|
Confirmed on local ECK setup that:
|
|
Pinging @elastic/es-security (Team:Security) |
n1v0lg
added
v9.0.0
v8.15.3
v8.16.0
auto-backport
|
Hi @n1v0lg, I've created a changelog YAML for you. |
…/elasticsearch into enable-cluster-state-role-mapper
n1v0lg
added
auto-merge-without-approval
💔 Backport failedThe backport operation could not be completed due to the following error: You can use sqren/backport to manually backport by running |
n1v0lg
added a commit
that referenced
this pull request
Oct 9, 2024
This PR default-enables cluster-state role mappings as the first part of the mitigation for a regression in ECK introduced by #107410. Prior to this PR, cluster-state role mappings were written to cluster-state, but not read from it. With this PR, cluster-state role mappings will be read and used to assign roles to users, i.e. in user role resolution. However, they will not be included in the output of the [Get role mappings API](https://www.elastic.co/guide/en/elasticsearch/reference/current/security-api-get-role-mapping.html) yet. Exposing them via API is a target for a follow-up fix. Relates: ES-9628 Supersedes: #113900
n1v0lg
added a commit
that referenced
this pull request
Oct 9, 2024
This PR default-enables cluster-state role mappings as the first part of the mitigation for a regression in ECK introduced by #107410. Prior to this PR, cluster-state role mappings were written to cluster-state, but not read from it. With this PR, cluster-state role mappings will be read and used to assign roles to users, i.e. in user role resolution. However, they will not be included in the output of the [Get role mappings API](https://www.elastic.co/guide/en/elasticsearch/reference/current/security-api-get-role-mapping.html) yet. Exposing them via API is a target for a follow-up fix. Relates: ES-9628 Supersedes: #113900
jakelandis
pushed a commit
that referenced
this pull request
Oct 9, 2024
This (backport) PR default-enables cluster-state role mappings as the first part of the mitigation for a regression in ECK introduced by #107410. Prior to this PR, cluster-state role mappings were written to cluster-state, but not read from it. With this PR, cluster-state role mappings will be read and used to assign roles to users, i.e. in user role resolution. However, they will not be included in the output of the [Get role mappings API](https://www.elastic.co/guide/en/elasticsearch/reference/current/security-api-get-role-mapping.html) yet. Exposing them via API is a target for a follow-up fix. Relates: ES-9628 Supersedes: #113900
matthewabbott
pushed a commit
to matthewabbott/elasticsearch
that referenced
this pull request
Oct 10, 2024
This PR default-enables cluster-state role mappings as the first part of the mitigation for a regression in ECK introduced by elastic#107410. Prior to this PR, cluster-state role mappings were written to cluster-state, but not read from it. With this PR, cluster-state role mappings will be read and used to assign roles to users, i.e. in user role resolution. However, they will not be included in the output of the [Get role mappings API](https://www.elastic.co/guide/en/elasticsearch/reference/current/security-api-get-role-mapping.html) yet. Exposing them via API is a target for a follow-up fix. Relates: ES-9628 Supersedes: elastic#113900
n1v0lg
added a commit
that referenced
this pull request
Oct 11, 2024
davidkyle
pushed a commit
to davidkyle/elasticsearch
that referenced
this pull request
Oct 13, 2024
This PR default-enables cluster-state role mappings as the first part of the mitigation for a regression in ECK introduced by elastic#107410. Prior to this PR, cluster-state role mappings were written to cluster-state, but not read from it. With this PR, cluster-state role mappings will be read and used to assign roles to users, i.e. in user role resolution. However, they will not be included in the output of the [Get role mappings API](https://www.elastic.co/guide/en/elasticsearch/reference/current/security-api-get-role-mapping.html) yet. Exposing them via API is a target for a follow-up fix. Relates: ES-9628 Supersedes: elastic#113900
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR default-enables cluster-state role mappings as the first part of the mitigation for a regression in ECK introduced by #107410.
Prior to this PR, cluster-state role mappings were written to cluster-state, but not read from it.
With this PR, cluster-state role mappings will be read and used to assign roles to users, i.e. in user role resolution.
However, they will not be included in the output of the Get role mappings API yet. Exposing them via API is a target for a follow-up fix.
Relates: ES-9628
Supersedes: #113900